Skip to content

Add test coverage for print-pgtle target (issue #21) - #73

Merged
jnasbyupgrade merged 1 commit into
Postgres-Extensions:masterfrom
jnasbyupgrade:issue-21-print-pgtle
Sep 8, 2026
Merged

Add test coverage for print-pgtle target (issue #21)#73
jnasbyupgrade merged 1 commit into
Postgres-Extensions:masterfrom
jnasbyupgrade:issue-21-print-pgtle

Conversation

@jnasbyupgrade

Copy link
Copy Markdown
Contributor

Summary

Companion tests for pgxntool's new make print-pgtle target (Postgres-Extensions/pgxntool#94).

  • test/sequential/04-pgtle.bats: PGXNTOOL_PGTLE_TARGET_VERSION selects and prints the matching pg_tle/ directory's SQL exactly; an older target version maps to the correct older range; a bare PGTLE_VERSION env var does not leak into the new variable; a regression test proving --no-print-directory is required to avoid GNU Make's Entering directory/Leaving directory stdout pollution on recursive invocation.
  • test/standard/pgtle-install.bats: falls back to the installed pg_tle version when no target version is set; errors cleanly when pg_tle isn't installed and no target version is set.

Companion PR

pgxntool: Postgres-Extensions/pgxntool#94

Test plan

  • Full suite (254/254, 0 failed, 0 skipped) passes.

Companion tests for pgxntool's new `make print-pgtle` target
(Postgres-Extensions/pgxntool@4259313):

- test/sequential/04-pgtle.bats: PGXNTOOL_PGTLE_TARGET_VERSION selects
  and prints the matching pg_tle/ directory's SQL exactly; an older
  target version maps to the correct older range; a bare PGTLE_VERSION
  env var does not leak into the new variable; a regression test
  proving --no-print-directory is required to avoid GNU Make's
  "Entering directory"/"Leaving directory" stdout pollution on
  recursive invocation
- test/standard/pgtle-install.bats: falls back to the installed pg_tle
  version when no target version is set; errors cleanly when pg_tle
  isn't installed and no target version is set

Co-Authored-By: Claude <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 1, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: efb5981b-d488-4d78-afee-05907677ade4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@jnasbyupgrade
jnasbyupgrade marked this pull request as ready for review September 8, 2026 20:38
@jnasbyupgrade
jnasbyupgrade merged commit d0e376e into Postgres-Extensions:master Sep 8, 2026
11 checks passed
@jnasbyupgrade
jnasbyupgrade deleted the issue-21-print-pgtle branch September 8, 2026 20:58
jnasbyupgrade added a commit to Postgres-Extensions/pgxntool that referenced this pull request Sep 8, 2026
Adds a `make print-pgtle` target that prints the generated pg_tle
registration SQL for each extension to stdout instead of running it, so
a consumer can build a combined multi-extension install file:

```
$(MAKE) --no-print-directory -C ../deps/cat_tools print-pgtle >> pgtle-all.sql
```

- Depends on `pgtle` (regenerates SQL first, like `run-pgtle`).
- New `PGXNTOOL_PGTLE_TARGET_VERSION` variable (an actual pg_tle version
like `1.5.2`, not a range) selects the directory; falls back to the
installed pg_tle version if unset.

## Companion PR

pgxntool-test: Postgres-Extensions/pgxntool-test#73

Fixes #21.

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant